IRIX Base Documentation 2001 May

home *** CD-ROM | disk | FTP | other *** search

/ IRIX Base Documentation 2001 May / SGI IRIX Base Documentation 2001 May.iso / usr / share / catman / a_man / cat1 / zic.z / zic

Wrap

Text File | 2001-04-17 | 13.1 KB | 331 lines

ZZZZIIIICCCC((((1111MMMM)))) ZZZZIIIICCCC((((1111MMMM)))) NNNNAAAAMMMMEEEE zic - time zone information compiler SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS _zzzz_iiii_cccc [ _----_vvvv] [ _----_dddd _d_i_r_e_c_t_o_r_y ] [ _----_llll _l_o_c_a_l_t_i_m_e ] [ _----_pppp _p_o_s_i_x_r_u_l_e_s ] [ _----_LLLL _l_e_a_p_s_e_c_o_n_d_f_i_l_e_n_a_m_e ] [ _----_ssss ] [ _----_yyyy _c_o_m_m_a_n_d ] [ _f_i_l_e_n_a_m_e ... ] DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN _ZZZZ_iiii_cccc reads text from the file(s) named on the command line and creates the time conversion information files specified in this input. If a _f_i_l_e_n_a_m_e is ----, the standard input is read. These options are available: ----dddd _d_i_r_e_c_t_o_r_y Create time conversion information files in the named directory rather than in the standard directory named below. ----llll _t_i_m_e_z_o_n_e Use the given time zone as local time. _Z_i_c will act as if the input contained a link line of the form Link _t_i_m_e_z_o_n_e localtime ----pppp _t_i_m_e_z_o_n_e Use the given time zone's rules when handling POSIX-format time zone environment variables. _Z_i_c will act as if the input contained a link line of the form Link _t_i_m_e_z_o_n_e posixrules ----LLLL _l_e_a_p_s_e_c_o_n_d_f_i_l_e_n_a_m_e Read leap second information from the file with the given name. If this option is not used, no leap second information appears in output files. _----_vvvv Complain if a year that appears in a data file is outside the range of years representable by _t_i_m_e(3) values. _----_ssss Limit time values stored in output files to values that are the same whether they're taken to be signed or unsigned. You can use this option to generate SVVS-compatible files. ----yyyy _c_o_m_m_a_n_d Use the given _c_o_m_m_a_n_d rather than _yyyy_eeee_aaaa_rrrr_iiii_ssss_tttt_yyyy_pppp_eeee when checking year types (see below). Input lines are made up of fields. Fields are separated from one another by any number of white space characters. Leading and trailing white space on input lines is ignored. An unquoted sharp character (#) in the input introduces a comment which extends to the end of the line the sharp character appears on. White space characters and sharp characters may be PPPPaaaaggggeeee 1111 ZZZZIIIICCCC((((1111MMMM)))) ZZZZIIIICCCC((((1111MMMM)))) enclosed in double quotes (") if they're to be used as part of a field. Any line that is blank (after comment stripping) is ignored. Non-blank lines are expected to be of one of three types: rule lines, zone lines, and link lines. A rule line has the form Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S For example: Rule US 1967 1973 - Apr lastSun 2:00 1:00 D The fields that make up a rule line are: _NNNN_AAAA_MMMM_EEEE Gives the (arbitrary) name of the set of rules this rule is part of. _FFFF_RRRR_OOOO_MMMM Gives the first year in which the rule applies. Any integer year can be supplied; the Gregorian calendar is assumed. The word _mmmm_iiii_nnnn_iiii_mmmm_uuuu_mmmm (or an abbreviation) means the minimum year representable as an integer. The word _mmmm_aaaa_xxxx_iiii_mmmm_uuuu_mmmm (or an abbreviation) means the maximum year representable as an integer. Rules can describe times that are not representable as time values, with the unrepresentable times ignored; this allows rules to be portable among hosts with differing time value types. _TTTT_OOOO Gives the final year in which the rule applies. In addition to _mmmm_iiii_nnnn_iiii_mmmm_uuuu_mmmm and _mmmm_aaaa_xxxx_iiii_mmmm_uuuu_mmmm (as above), the word _oooo_nnnn_llll_yyyy (or an abbreviation) may be used to repeat the value of the _FFFF_RRRR_OOOO_MMMM field. _TTTT_YYYY_PPPP_EEEE Gives the type of year in which the rule applies. If _TTTT_YYYY_PPPP_EEEE is _---- then the rule applies in all years between _FFFF_RRRR_OOOO_MMMM and _TTTT_OOOO inclusive. If _TTTT_YYYY_PPPP_EEEE is something else, then _z_i_c executes the command yyyyeeeeaaaarrrriiiissssttttyyyyppppeeee _y_e_a_r _t_y_p_e to check the type of a year: an exit status of zero is taken to mean that the year is of the given type; an exit status of one is taken to mean that the year is not of the given type. _IIII_NNNN Names the month in which the rule takes effect. Month names may be abbreviated. _OOOO_NNNN Gives the day on which the rule takes effect. Recognized forms include: 5 the fifth of the month lastSun the last Sunday in the month lastMon the last Monday in the month Sun>=8 first Sunday on or after the eighth Sun<=25 last Sunday on or before the 25th Names of days of the week may be abbreviated or spelled out in PPPPaaaaggggeeee 2222 ZZZZIIIICCCC((((1111MMMM)))) ZZZZIIIICCCC((((1111MMMM)))) full. Note that there must be no spaces within the _OOOO_NNNN field. _AAAA_TTTT Gives the time of day at which the rule takes effect. Recognized forms include: 2 time in hours 2:00 time in hours and minutes 15:00 24-hour format time (for times after noon) 1:28:14 time in hours, minutes, and seconds Any of these forms may be followed by the letter _wwww if the given time is local "wall clock" time, _ssss if the given time is local "standard" time, or _uuuu (or _gggg or zzzz) if the given time is universal time; in the absence of an indicator, wall clock time is assumed. _SSSS_AAAA_VVVV_EEEE Gives the amount of time to be added to local standard time when the rule is in effect. This field has the same format as the _AAAA_TTTT field (although, of course, the _wwww and _ssss suffixes are not used). _LLLL_EEEE_TTTT_TTTT_EEEE_RRRR_////_SSSS Gives the "variable part" (for example, the "S" or "D" in "EST" or "EDT") of time zone abbreviations to be used when this rule is in effect. If this field is ----, the variable part is null. A zone line has the form Zone NAME GMTOFF RULES/SAVE FORMAT [UNTIL] For example: Zone Australia/Adelaide 9:30 Aus CST 1971 Oct 31 2:00 The fields that make up a zone line are: _NNNN_AAAA_MMMM_EEEE The name of the time zone. This is the name used in creating the time conversion information file for the zone. _GGGG_MMMM_TTTT_OOOO_FFFF_FFFF The amount of time to add to GMT to get standard time in this zone. This field has the same format as the _AAAA_TTTT and _SSSS_AAAA_VVVV_EEEE fields of rule lines; begin the field with a minus sign if time must be subtracted from GMT. _RRRR_UUUU_LLLL_EEEE_SSSS_////_SSSS_AAAA_VVVV_EEEE The name of the rule(s) that apply in the time zone or, alternately, an amount of time to add to local standard time. If this field is _---- then standard time always applies in the time zone. _FFFF_OOOO_RRRR_MMMM_AAAA_TTTT The format for time zone abbreviations in this time zone. The pair of characters _%%%%_ssss is used to show where the "variable part" of the time zone abbreviation goes. Alternately, a slash (/) separates PPPPaaaaggggeeee 3333 ZZZZIIIICCCC((((1111MMMM)))) ZZZZIIIICCCC((((1111MMMM)))) standard and daylight abbreviations. _UUUU_NNNN_TTTT_IIII_LLLL The time at which the GMT offset or the rule(s) change for a location. It is specified as a year, a month, a day, and a time of day. If this is specified, the time zone information is generated from the given GMT offset and rule change until the time specified. The month, day, and time of day have the same format as the IN, ON, and AT columns of a rule; trailing columns can be omitted, and default to the earliest possible value for the missing columns. The next line must be a "continuation" line; this has the same form as a zone line except that the string "Zone" and the name are omitted, as the continuation line will place information starting at the time specified as the _UUUU_NNNN_TTTT_IIII_LLLL field in the previous line in the file used by the previous line. Continuation lines may contain an _UUUU_NNNN_TTTT_IIII_LLLL field, just as zone lines do, indicating that the next line is a further continuation. A link line has the form Link LINK-FROM LINK-TO For example: Link Europe/Istanbul Asia/Istanbul The _LLLL_IIII_NNNN_KKKK_----_FFFF_RRRR_OOOO_MMMM field should appear as the _NNNN_AAAA_MMMM_EEEE field in some zone line; the _LLLL_IIII_NNNN_KKKK_----_TTTT_OOOO field is used as an alternate name for that zone. Except for continuation lines, lines may appear in any order in the input. Lines in the file that describes leap seconds have the following form: Leap YEAR MONTH DAY HH:MM:SS CORR R/S For example: Leap 1974 Dec 31 23:59:60 + S The YYYYEEEEAAAARRRR, MMMMOOOONNNNTTTTHHHH, DDDDAAAAYYYY, and _HHHH_HHHH_::::_MMMM_MMMM_::::_SSSS_SSSS fields tell when the leap second happened. The _CCCC_OOOO_RRRR_RRRR field should be "+" if a second was added or "-" if a second was skipped. The _RRRR_////_SSSS field should be (an abbreviation of) "Stationary" if the leap second time given by the other fields should be interpreted as GMT or (an abbreviation of) "Rolling" if the leap second time given by the other fields should be interpreted as local wall clock time. NNNNOOOOTTTTEEEE For areas with more than two types of local time, you may need to use local standard time in the _AAAA_TTTT field of the earliest transition time's rule to ensure that the earliest transition time recorded in the compiled PPPPaaaaggggeeee 4444 ZZZZIIIICCCC((((1111MMMM)))) ZZZZIIIICCCC((((1111MMMM)))) file is correct. FFFFIIIILLLLEEEE /usr/lib/locale/TZ standard directory used for created files AAAAUUUUTTTTHHHHOOOORRRR This version is based on the public domain code written by Arthur David Olson. SSSSEEEEEEEE AAAALLLLSSSSOOOO zdump(1M), ctime(3). PPPPaaaaggggeeee 5555